Skip to content

Prepare 0.2.1 for npm provenance publish and n8n verification - #3

Merged
ivodraginov-cloud merged 1 commit into
mainfrom
fix/0.2.1-verification-publish
Nov 11, 2026
Merged

ivodraginov-cloud merged 1 commit into
mainfrom
fix/0.2.1-verification-publish

Conversation

@ivodraginov-cloud

Copy link
Copy Markdown
Contributor

Why

n8n-nodes-batchdata 0.2.0 was published from a local machine on Nov 9 with the old repository.url (batchdataco/batchdata-n8n-node) and no npm provenance. n8n will not verify a node published that way (required since May 1, 2026). This prepares 0.2.1 so .github/workflows/publish.yml can publish from a version tag with provenance, pointing at this repo.

Changes

  • Bump to 0.2.1. package.json already has the correct repository.url and homepage from Fix repository/homepage URLs to match this repo (needed for npm provenance) #2.
  • n8n-only cost-safety overrides (shared catalog.json is unchanged): Get Property Permits, Find Investors, and Get Investor Properties default to 1 result; the billed search-session trigger defaults to 5 per check; Property Search Limit defaults to 1.
  • HTTP 402 now explains that the account balance is too low.
  • README: published status, current Creator Portal docs link, single license section.
  • Regression tests for the defaults, row-level Your Reference ID on batch operations, package metadata, and the 402 message.

Lint, build, and all 40 tests passed locally.

After merge

Push the 0.2.1 tag to trigger publish.yml. The NPM_TOKEN Actions secret is already set. Then submit https://www.npmjs.com/package/n8n-nodes-batchdata through the n8n Creator Portal.

Fix the package metadata so a GitHub Actions publish can attest this
repo, and apply the Zapier 0.4.2 cost-safety defaults as n8n-only
overrides: billed list operations default to 1 result, the billed
search-session trigger defaults to 5 per check, and HTTP 402 explains
a low balance. Add regression tests for those defaults, row-level
reference IDs, and the 402 message.
@ivodraginov-cloud
ivodraginov-cloud merged commit f5e4af0 into main Nov 11, 2026
1 check passed
@ivodraginov-cloud
ivodraginov-cloud deleted the fix/0.2.1-verification-publish branch November 11, 2026 16:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants